This simplifies some common logic used by detectors a little more.

This should not change the logic, except for one small bug that this is fixing: we have some logic that prevents triggering a package.json scripts whose command includes netlify dev (to prevent infinite recursion). However, it was still possible to have netlify dev triggered by Netlify Dev when the script included one of the frameworks' preferredCommand. For example:

"scripts": {
  "build": "netlify dev && gatsby develop"
}